Lucene search
K
LinuxLinux Kernel6.12.25

6 matches found

CVE
CVE
added 2025/05/20 4:47 p.m.81 views

CVE-2025-37965

Concretely described CVE-2025-37965 affects the Linux kernel DRM/AMD display code. The root cause is GFP_KERNEL memory allocations in populate_dml_plane_cfg_from_plane_state(), which are unsafe in atomic contexts. The fix removes dynamic allocations by passing a pointer to scaler_data within the ...

5.5CVSS6.5AI score0.00146EPSS
CVE
CVE
added 2025/07/03 8:35 a.m.80 views

CVE-2025-38151

Technical details about CVE-2025-38151 are not publicly provided in the supplied documents; no explicit information on affected kernel versions, root cause, impact, or patch is included. Monitor for updates.

5.5CVSS7AI score0.00147EPSS
CVE
CVE
added 2025/07/25 3:27 p.m.77 views

CVE-2025-38451

CVE-2025-38451 affects the Linux kernel’s md/md-bitmap code. The issue caused a GPF in bitmap_get_stats() when handling external or internal bitmaps due to missing super-block validation. The fix adds a super-block existence check for both internal and external cases, preventing the non-canonical...

5.5CVSS6.5AI score0.00147EPSS
CVE
CVE
added 2026/05/28 9:35 a.m.60 views

CVE-2026-46124

CVE-2026-46124 affects the Linux kernel isofs filesystem. The vulnerability arises because isofs_fh_to_dentry/isofs_fh_to_parent pass an attacker-controlled block number from an NFS file handle to isofs_export_iget(), which only rejects block == 0 before calling isofs_iget and sb_bread. A crafted...

7.5CVSS5.8AI score0.00425EPSS
CVE
CVE
added 2025/07/02 2:43 p.m.51 views

CVE-2025-38092

CVE-2025-38092 concerns the Linux kernel (ksmbd) and the opinfo_get_list() path. The root cause is use of list_first_entry(), which does not return NULL for empty lists, leading to an invalid pointer. The fix is to switch to list_first_entry_or_null() to safely detect empties. Public references i...

5.5CVSS6.7AI score0.00136EPSS
CVE
CVE
added 2026/05/08 2:21 p.m.33 views

CVE-2026-43376

CVE-2026-43376 affects ksmbd in the Linux kernel. The vulnerability arises from freeing oplock_info with kfree() while it can still be accessed under RCU read-side critical sections (e.g., opinfo_get), allowing a use-after-free. The fixes across connected reports switch to deferred freeing via ca...

9.8CVSS5.8AI score0.00444EPSS